Location reporting for service enabler architecture layer (seal)

ABSTRACT

A method of a service enabler architecture layer (SEAL) can include receiving a location reporting configuration at a first user equipment (UE) from a location management server of the SEAL. The location reporting configuration can indicate at least one location reporting event for triggering a first location information report from a first location management client at the first UE to the location management server. The first location information report can be transmitted to the location management server from the first location management client at the first UE in response to the at least one location reporting event occurring. The first location information report can include an identity of the first UE, an identity of the at least one location reporting event that triggers the first location information report, first location information of the first UE, and a first timestamp corresponding to the first location information of the first UE.

INCORPORATION BY REFERENCE

This present disclosure claims priority to U.S. Provisional ApplicationNo. 63/172,050, “A Method of Supporting Location Timestamp Reporting for3GPP SEAL Architecture” filed on Apr. 7, 2021, which is incorporated byreference herein in its entirety.

TECHNICAL FIELD

The present disclosure describes embodiments generally related to aservice enabler layer for supporting vertical applications operatingover a wireless network.

BACKGROUND

The background description provided herein is for the purpose ofgenerally presenting the context of the disclosure. Work of thepresently named inventors, to the extent the work is described in thisbackground section, as well as aspects of the description that may nototherwise qualify as prior art at the time of filing, are neitherexpressly nor impliedly admitted as prior art against the presentdisclosure.

Wireless communication systems are being designed with advanced built-infeatures to support enterprise segments or vertical industries such ashealth care, automotive, smart factories, mission-criticalcommunications, and the like. Vertical application standards are beingdeveloped to enable rapid deployment of vertical services based oncommon services provided by wireless networks. A vertical domain can bean industry or a group of enterprises in which similar products orservices are produced. A vertical application can provide services orfunctions useful in a specific vertical domain.

SUMMARY

Aspects of the disclosure provide a method of a service enablerarchitecture layer (SEAL). The method can include receiving a locationreporting configuration at a first user equipment (UE) from a locationmanagement server of the SEAL. The location reporting configuration canindicate at least one location reporting event for triggering a firstlocation information report from a first location management client atthe first UE to the location management server. The first locationinformation report can be transmitted to the location management serverfrom the first location management client at the first UE in response tothe at least one location reporting event occurring. The first locationinformation report can include an identity of the first UE, an identityof the at least one location reporting event that triggers the firstlocation information report, first location information of the first UE,and a first timestamp corresponding to the first location information ofthe first UE.

In an embodiment, a format of the first timestamp corresponding to thefirst location information of the first UE is one of:

yyyy-month-dayTHH:MM:SS,

Monday, DD Mon YYYY HH:MM:SS TimeZone, and

yyyy-mn-ddTHH:MM:SS.

An embodiment of the method can further include receiving a locationinformation request from the location management server of the SEAL,and, in response to the received location information request,transmitting a second location information report to the locationmanagement server. The second location information report can includesecond location information of the first UE and a second timestampcorresponding to the second location information of the first UE.

An embodiment of the method can further include transmitting a locationreporting trigger to the location management server to activate alocation reporting process for obtaining third location information of asecond location management client of the SEAL at a second UE. A thirdlocation information report can be received from the location managementserver, the third location information report including the thirdlocation information of the second UE and a third timestampcorresponding to the third location information of the second UE.

In an embodiment, a type of the first location information identified inthe location reporting configuration is one of an E-UTRA cell globalidentifier (ECGI), a multimedia broadcast multicast services servicearea identity (MBMS SAI), and geographic coordinates.

An embodiment of the method can further include transmitting a locationinformation subscription request including a location informationsubscription configuration to the location management server. A locationinformation notification can be received from the location managementserver. The location information notification can include an identity ofa third UE, an identity of the first UE, an identity of an event thattriggered the location information notification, latest locationinformation of the third UE, and a fourth timestamp associated with thelatest location information of the third UE.

Aspects of the disclosure can provide another method of a SEAL. Themethod can include transmitting from a location management server alocation reporting configuration to a first location management clientof the SEAL at a first UE. The location reporting configuration canindicate at least one location reporting event for triggering a firstlocation information report from the first location management client ofthe SEAL at the first UE to the location management server. The firstlocation information report can be received from the first locationmanagement client of the SEAL at the first UE. The first locationinformation report can include an identity of the first UE, an identityof the at least one location reporting event that triggers the firstlocation information report, first location information of the first UE,and a first timestamp corresponding to the first location information ofthe first UE. The first location information of the first UE can bestored in a memory.

Aspects of the disclosure can provide a non-transitory computer-readablemedium storing instructions. The instructions, when executed by aprocessor, can cause the processor to perform the above methods.

BRIEF DESCRIPTION OF THE DRAWINGS

Further features, the nature, and various advantages of the disclosedsubject matter will be more apparent from the following detaileddescription and the accompanying drawings in which:

FIG. 1 shows a generic on-network functional model (100) according to anembodiment of the disclosure.

FIG. 2 shows an exemplary on-network location management functionalmodel (200) according to some embodiments of the disclosure.

FIG. 3 shows an event-triggered location reporting process (300)according to some embodiments of the disclosure.

FIG. 4 shows an on-demand location reporting process (400) according tosome embodiments of the disclosure.

FIG. 5 shows a client-triggered or VAL server-triggered locationreporting process (500) according to some embodiments of the disclosure.

FIG. 6 shows a location information subscription and notificationprocess (600) according to some embodiments of the disclosure.

FIG. 7 shows a location reporting process (700) according to anembodiment of the disclosure.

FIG. 8 shows a location reporting process (800) according to anembodiment of the disclosure.

FIG. 9 is a schematic illustration of a computer system in accordancewith an embodiment.

DETAILED DESCRIPTION OF EMBODIMENTS

I. Service Enabler Layer for Verticals

1. Service Enabler Architecture Layer (SEAL)

Embodiments of the disclosure implement a service enabler layer forsupporting vertical applications (or verticals). The service enablerlayer can be referred to as a service enabler architecture layer (SEAL)in this disclosure. The SEAL can provide a common set of capabilities(or services) used by multiple verticals to accelerate the developmentand deployment of vertical applications. For example, instead ofdeveloping auxiliary services specific to each vertical, commonly neededauxiliary services can be captured into the SEAL and shared by multiplevertical applications. Usage of all SEAL services by a verticalapplication can be optional. A vertical application can decide to useany subset of services from the SEAL.

2. Generic Functional Model for SEAL Services

In some embodiments, a functional model for SEAL can be organized into ageneric SEAL service functional model and multiple specific SEAL servicefunctional models. The generic SEAL service functional model can be usedas a reference model for the specific SEAL service functional models.The generic functional model can include an on-network functional modeland an off-network functional model. In various embodiments, the SEALservices provided to support the vertical application layer can includelocation management, group management, configuration management,identity management, key management, network resource management, andthe like.

FIG. 1 shows a generic on-network functional model (100) according to anembodiment of the disclosure. The model (100) can include four types offunctional entities: a vertical application layer (VAL) client (111), aVAL server (121), a SEAL client (112), and a SEAL server (122). Thenumber of each type of functional entities in the model (100) can be oneor more than one. The VAL client and the VAL server entities can belongto a VAL (101). The SEAL client and the SEAL server entities can belongto a SEAL (102). The VAL client (111) and the SEAL client (112) can beincluded in a user equipment (UE) (110). The model (100) furtherincludes a wireless network system (140) (such as a Third GenerationPartnership Project (3GPP) network system). The elements can be coupledtogether as shown in FIG. 1.

In the VAL (101), the VAL client (111) communicates with the VAL server(121) over a VAL-UU reference point (134) corresponding to a VAL-UUinterface. In an example, the VAL-UU interface supports both unicast andmulticast delivery modes.

The SEAL (102) offers various services to the VAL (101). The SEALclient(s) communicates with the SEAL server(s) over a SEAL-UU referencepoint(s) (133) corresponding to a SEAL-UU interface. The SEAL-UUinterface supports both unicast and multicast delivery modes. The SEALclient(s) provides the service enabler layer support functions to theVAL client(s) over a SEAL-C reference point (131) (corresponding to aSEAL-C interface). The VAL server(s) communicates with the SEALserver(s) over a SEAL-S reference point(s) (corresponding to a SEAL-Sinterface). The SEAL server(s) (122) may communicate with the underlying3GPP network system (140) using a respective 3GPP interface (135)specified by the 3GPP network system.

For a specific service (such as the location management service), aspecific SEAL client and a specific SEAL server along with theirspecific SEAL-UU reference point and the specific network interface ofthe 3GPP network system can form or belong to a specific on-networkfunctional model.

In some embodiments, to support distributed SEAL server deployments, aSEAL server may interact with another SEAL server for the same SEALservice over a so-called SEAL-E reference point (not shown in FIG. 1). ASEAL server can interact with another SEAL server for inter-servicecommunication over a so-called SEAL-X reference point (not shown in FIG.1). A SEAL server may interact with a VAL user database for storing andretrieving a user profile over a VAL-UDB reference point.

In various embodiments, functional entities in a VAL system (forexample, including the VAL 101 and the SEAL 102) can provide applicationcontrol and media-specific functions to support one or more VALservices. In the FIG. 1 example, the VAL client (111) (e.g., avehicle-to-everything (V2X) client) can provide client-sidefunctionalities corresponding to a vertical application (e.g., a V2Xapplication). The VAL client (111) can support the verticalapplication's interactions with the SEAL client(s) (112). The VAL server(121) (e.g. a V2X application server) can provide server-sidefunctionalities corresponding to the vertical application.

In the FIG. 1 example, the SEAL client (112) can provide client-sidefunctionalities corresponding to a specific SEAL service (e.g., locationmanagement, network resource management, or the like). The SEAL client(112) can support interactions with the VAL client(s) (111). The SEALclient can also support interactions with a corresponding SEAL clientbetween the two UEs. The SEAL server (122) can provide server-sidefunctionalities corresponding to the specific SEAL service. The SEALserver (122) can support interactions with the VAL server(s) (121). TheSEAL server can also support interactions with the corresponding SEALserver in distributed SEAL deployments.

It is noted that the functional entities in the model (100) can beimplemented in various ways in different embodiments. For example, thefunctional entities can be implemented in a distributed manner or acentralized manner. The functional entities can be implemented assoftware or a combination of software and hardware.

In the FIG. 1 example, the VAL user database (not shown) can containinformation of user profiles associated with a VAL service provided by aVAL service provider. Typically, each VAL service may have acorresponding user database, such as a mission critical push to talk(MCPTT) user database, a mission critical video (MCVideo) user database,and a mission critical data (MCData) user database.

In some embodiments, the interactions related to the VAL (101) supportfunctions between the VAL client (111) and the VAL server (121) aresupported by the VAL-UU reference point (134). In an example, thisreference point (134) is an instance of a Uu reference point asdescribed in 3GPP TS 23.401 and 3GPP TS 23.501. In some embodiments, theinteractions related to VAL support functions between the VAL clients oftwo UEs can be supported by a VAL-PC5 reference point (not shown). Forexample, this reference point can be an instance of a PC5 referencepoint as described in 3GPP TS 23.303.

In some embodiments, the interactions between a SEAL client (112) andthe corresponding SEAL server (122) are supported by a SEAL-UU referencepoint (133). The specific SEAL service reference point corresponding tothe SEAL-UU (133) can be specified in a specific SEAL service functionalmodel. In some embodiments, the interactions between the SEAL clients oftwo VAL UEs can be supported by a SEAL-PC5 reference point (not shown).The specific SEAL service reference point corresponding to the SEAL-PC5can be specified in a specific SEAL service functional model.

In some embodiments, the interactions between the VAL client(s) (111)and the SEAL client(s) (112) within the VAL UE (110) are supported by aSEAL-C reference point (131). The specific SEAL service reference pointcorresponding to the SEAL-C (131) can be specified in a specific SEALservice functional model.

In some embodiments, the interactions between the VAL server (121) andthe SEAL server (132) are supported by a SEAL-S reference point (132). Aspecific SEAL service reference point corresponding to the SEAL-S (132)can be specified in the specific SEAL service functional model.

In some embodiments, the interactions between the SEAL servers of thesame type (e.g., providing a same type of SEAL service) are supported bya SEAL-E reference point (not shown). The specific SEAL servicereference point corresponding to the SEAL-E is specified in the specificSEAL service functional model.

In some embodiments, the interactions between the SEAL servers ofdifferent types can be supported by a SEAL-X reference point. Examplesof specific reference points corresponding to the SEAL-X referencepoints can include a reference point SEAL-X1 between a key managementserver and a group management server, a reference point SEAL-X2 betweena group management server and a location management server.

A reference point VAL-UDB exists between a VAL user database and a SEALserver. The reference point VAL-USB can be used for storing the userprofile data in a specific VAL user database and obtaining the userprofile from the specific VAL user database for further configuration ina UE.

3. Identities

In various embodiments, different identities can be configured and usedin a VAL system developed based on the model (100). In some embodiments,a VAL user can present a user identity (User ID) to an identitymanagement server in the SEAL (102) during a user authenticationtransaction to provide an identity management client a means for VALservice authentication. In general, since identity management is acommon SEAL service, the identity management server uses a set ofcredentials (e.g. biometrics, secureID, username/password) that may notnecessarily be tied to a single VAL service. The user credentialsuniquely identify the VAL user to the identity management server. As anexample, the specific security and authentication mechanisms required inorder to use the user ID is specified in 3GPP TS 33.434.

In some embodiments, a VAL user ID is a unique identifier within the VALservice that represents the VAL user. For example, the VAL user ID maybe a URI. The VAL user ID is used for authentication and authorizationpurposes for providing the VAL service towards the VAL user via a VALUE. The VAL user ID also indicates a VAL service provider with which theVAL user has a VAL service agreement. The VAL user may have a VALservice agreement with a VAL service provider and thus have obtained aunique VAL user ID per a VAL service provider. The VAL user ID can beused to access a SEAL service.

In some embodiments, a VAL UE ID is a unique identifier within a VALservice that represents the VAL UE. For example, the VAL UE ID for a V2Xservice is mapped to a Station ID as specified in ETSI TS 102 894-2. TheVAL UE ID is used to address the VAL UE in order to send VAL messages.

In some embodiments, a VAL service ID is a unique identifier thatrepresents a VAL service. A VAL server provides a list of VAL servicestowards VAL users or VAL UEs. Each VAL service is uniquely identified bya VAL service ID, which is an identifier of the VAL applicationproviding that VAL service. The VAL service ID can be used for policymapping, QoS handling for VAL communication and VAL messagedistribution. For example, an identifier of a V2X service, e.g. ITS-AIDor PSID specified in ETSI TS 102 965 and ISO TS 17419, can be used as aV2X service ID.

In some embodiments, a VAL group ID is a unique identifier within a VALservice that represents a set of VAL users or VAL UEs according to theVAL service. The set of VAL users may belong to the same or differentVAL service providers. The VAL group ID indicates the VAL applicationserver where the group is defined.

In some embodiments, a VAL system ID is a globally unique identifierrepresenting a VAL system. In some embodiments, a VAL Stream ID is anidentity used by the VAL server to identify a VAL stream.

4. Application of Functional Model to Deployments

In various embodiments, the SEAL architecture as described above cansupport deployments in which SEAL services are deployed within and/oroutside a public land mobile network (PLMN) network. The SEALarchitecture can also support centralized as well as distributeddeployments of vertical applications. A mobile network operator (MNO)can leverage an appropriate deployment model according to need and thatis suitable to its business.

A deployment model can involve multiple entities, such as VAL users, VALservice providers, SEAL providers, and PLMN operators. As an example, ina possible deployment model, SEAL server(s) can be deployed within aPLMN operator domain, and vertical application servers can be deployedin a VAL service provider domain. SEAL servers can also interact withanother SEAL server of a same SEAL service, which is deployed in adifferent PLMN operator domain, using a SEAL-E interface.

There can be possibilities of multiple business relationships amongentities involved in a deployment. Based on a service-specificagreement, VAL Users belong to a VAL service provider domain. A VALservice provider and a home PLMN operator may belong to a sameorganization. The VAL service provider can have a service agreement witha SEAL service provider. It is also possible that the VAL serviceprovider, the SEAL service provider, and the home PLMN operator belongto the same organization. The VAL service provider and the home PLMNoperator may have a service agreement if they do not belong to the sameorganization.

5. V2X Vertical Application Based on SEAL

In an embodiment, a V2X vertical application is developed based on SEALservices. The SEAL can support multiple SEAL services. Each SEAL servicecan support multiple processes. Typically, a SEAL client will notinitiate a process itself. In order for the SEAL client to start aprocess, the V2X vertical application needs to provide triggers andparameters related to the process to the SEAL client.

For example, a V2X application-level functional model is defined in 3GPPTS 23.286. As defined, a V2X application enabler (VAE) layer providesVAE capabilities for a V2X application specific layer. The VAE layerutilizes SEAL services. A VAE client can act as a VAL client forinteractions with a SEAL client as specified by the SEAL architecture. AVAE server can act as a VAL server for interactions with a SEAL serveras specified by the SEAL architecture.

The V2X application layer can provide a group joining strategy and agroup leader for each group. The VAE client and the VAE server use aSEAL group management service for group management operations. The V2Xapplication layer is responsible for deciding when to create, modify ordelete groups. Before a V2X UE starts to receive a V2X service from theV2X application layer, the VAE client and the VAE server can use theSEAL configuration management service to provide configurations to theV2X UE. When the V2X UE has received the V2X service from the V2Xapplication layer, the VAE client and the VAE server can also use theSEAL configuration management service to provide configuration updatesto the V2X UE.

The VAE client and VAE server can use a SEAL location management serviceto manage the location information of a V2X UE and update locationinformation to the V2X application layer. The VAE client and the VAEserver can use a SEAL identity management service to authenticate andauthorize the V2X UE for using a V2X application server. The VAE clientand the VAE server can use a SEAL network resource management service toestablish, modify and switch between different types of bearers.

The VAE server can also use a SEAL API to use SEAL services to enabledifferent functions or services of the V2X application. For example, tocreate a group for a V2X application, the VAE server can invoke a createservice operation of the group management API on a GM-S reference point.A group management server can create a group document and notify the VAEserver of the newly created group information.

In various embodiments, multiple vertical applications can use SEALservices at the same time. For example, two vertical applications V2Xand MCPTT can use SEAL services. A SEAL server can interface with bothvertical application servers. In addition, each vertically specific UEcan include a SEAL client that provides services to vertical applicationclients. The two SEAL clients interact with the SEAL server to providesupport to the two vertical applications.

II. Location Management Service

1. Functional Model for Location Management

In various embodiments, location management of a SEAL service offerslocation management related capabilities to one or more verticalapplications. The location management can be implemented based on alocation management functional model. The location management functionalmodel can be based on the generic functional model described above. Thelocation management functional model can include an on-networkfunctional model and an off-network functional model.

FIG. 2 shows an exemplary on-network location management functionalmodel (200) according to some embodiments. The model (200) can include aVAL client (211), a VAL server (221), a location management client(212), and a location management server (222). The functional entitiescan be coupled together as shown in FIG. 2.

The VAL client (211) and the VAL server (221) belong to a VAL (201). Thelocation management client (212) and the location management server(222) belong to a SEAL (202). The VAL client (211) and the locationmanagement client (212) can be included in a UE (210). The model (200)can also include a wireless work system (240) (such as a 3GPP networksystem) that provides communication paths for the UE (210) tocommunicate with the VAL server (221) and the location management server(222). It is noted that there can be multiple VAL clients in place ofthe VAL client (211) in the model (200) that use the location managementSEAL service provided by the location management client (212) and thelocation management server (222). Also, there can be multiple VALservers in place of the VAL server (221) in the model (200) that use thelocation management SEAL service provided by the location managementclient (212) and the location management server (222).

In some embodiments, the location management client (212) communicateswith the location management server (222) over an LM-UU reference point(233). The location management client (222) provides the support forlocation management functions to the VAL client (211) over an LM-Creference point (231). The VAL server (221) communicates with thelocation management server (222) over an LM-S reference point (232). TheVAL client (211) communicates with the VAL server (221) over a VAL-UUreference point (234).

In some embodiments, the location management server (222) communicateswith the underlying wireless communication system (240) to obtainlocation information via an interface (235) (e.g., T8 interface). In anexample, the location management server (222) communicates with aservice capability exposure function (SCEF) via a T8 interface (235) toobtain location information from the underlying 3GPP network system. Inan example, the location management server (222) can obtain locationinformation from a location server (LCS) of a 4G system using anotherinterface. In an example, the location management server (222) canobtain location information via an Le interface from the 3GPP networksystem (240).

In an off-network location management functional model, VAL clients in aVAL distributed in different UEs can communicate with each other over aVAL-PC5 reference point. Location management clients in a SEALdistributed in different UEs can communicate with each other over anLM-PC5 reference point.

In some embodiments, the location management client (212) interacts withthe VAL client (211) to perform location management functions. Thelocation management client (212) also interacts with the locationmanagement server (222). The location management client (212) alsosupports interactions with a corresponding location management clientbetween the two UEs.

In some embodiments, the location management server (222) receives andstores user location information and provides user location informationto the VAL server (221). The location management server (222) may alsoacquire location information provided by a PLMN operator of the 3GPPnetwork system (240) via, for example, the T8 interface (235). Thelocation management server (222) also supports interactions with acorresponding location management server in distributed SEALdeployments.

The VAL client (211) and the VAL server (221) can function in a similarway as the VAL client (111) and the VAL server (121), respectively, inthe FIG. 1 example.

In some embodiments, the interactions related to location managementfunctions between the location management client (212) and the locationmanagement server (222) are supported by the LM-UU reference point(233). In an example, this reference point (233) utilizes a Uu referencepoint as described in 3GPP TS 23.401 and 3GPP TS 23.501. The LM-UUreference point (233) provides a means for the location managementserver (222) to receive a location information report from the locationmanagement client (212).

In some embodiments, the interactions related to location managementfunctions between the location management clients located in differentVAL UEs are supported by an LM-PC5 reference point. In an example, thisreference point utilizes a PC5 reference point as described in 3GPP TS23.303. In some embodiments, the interactions related to locationmanagement functions between the VAL client(s) (211) and the locationmanagement client (212) within the VAL UE (210) are supported by theLM-C reference point (231).

In some embodiments, the interactions related to location managementfunctions between the VAL server(s) (221) and the location managementserver (222) are supported by the LM-S reference point (232). In anexample, this reference point (232) is an instance of CAPIF-2 referencepoint as specified in 3GPP TS 23.222. For example, the LM-S referencepoint (232) is used by the VAL server (221) to request and receivelocation information from the location management server (222).

In some embodiments, the interactions related to location managementfunctions between the location management servers in a distributeddeployment are supported by an LM-E reference point. In someembodiments, the T8 interface (235) supports the interactions betweenthe location management server (222) and an SCEF that is specified in3GPP TS 23.682. The functions related to location management of T8 aresupported by the location management server (222).

2. Examples of Location Management Processes

2.1 Event-Triggered Location Reporting Process

FIG. 3 shows an event-triggered location reporting process (300)according to some embodiments of the disclosure. The process (300) canbe performed by a location management client (301) and a locationmanagement server (302). The process (300) can start at (S310).

At (S310), the location management client (301) can transmit a locationreporting configuration request message to the location managementserver (302) to fetch a location reporting configuration.

At (S320), the location management server (302) can transmit a locationreporting configuration response message to the location managementclient (301) in response to receiving the location reportingconfiguration request message. The location reporting configurationresponse message can include the location reporting configuration. Thelocation reporting configuration can be an initial configuration or anupdate to a prior configuration. The location reporting configurationcan indicate what types of location information the location managementserver (302) expects and what events will trigger the sending oflocation information to the location management server (302).

In some embodiments, the decision to report location information can betriggered at the location management client (301) by various conditionsor events, e.g., reception of a location reporting configuration, aninitial registration to a wireless network, a distance travelled, anelapsed time, a cell change, an MBMS SAI change, an MBMS session change,leaving a specific MBMS bearer service area, a tracking area change, aPLMN change, a call initiation, an emergency, or other types of events.In an embodiment, the location reporting configuration can furtherindicate a minimum time between consecutive reports. In an embodiment,the location reporting configuration can further indicate whether atimestamp of the location information report is needed.

In some embodiments, the location reporting configuration responsemessage can be sent over a unicast bearer to a specific locationmanagement client (e.g., the location management client (301)) or as agroup message over an MBMS bearer to update the location reportingconfiguration for multiple location management clients at the same time.In an example, if the multicast delivery mode is used, the MBMS bearerbeing used is activated by the location management server.

In some embodiments, the location management client (301) stores orupdates the location reporting event triggers configuration in responseto receiving the location reporting configuration. In an example, thelocation reporting configuration information can be made part of theuser profile. In such a scenario, the sending of the locationinformation configuration response message is not necessary. In someembodiments, different location management clients may be givendifferent location reporting criteria.

At (S330), the location management client (301) can detect that aconfigured location reporting event occurs. Accordingly, a locationinformation report can be triggered.

At (S340), the location management client (301) can transmit thelocation information report to the location management server (302). Thelocation information report can include location information identifiedby the location management server (302) and available to the locationmanagement client (301).

In an embodiment, the location information report can include one ormore of the following information elements: (1) An identity of a VALuser or VAL UE corresponding to the location management client (301).For example, the VAL UE contains the location management client (301).The VAL user uses the service of the location management client (301)via a VAL client above the location management client (301). (2) Anidentity of the event that triggered the transmission of the locationinformation report. (3) Location information of the VAL UE when theevent that triggered the transmission of the location information reporttakes place. (4) Optionally, a timestamp of the location informationreport. For example, the timestamp can indicate a time when the eventthat triggered the transmission of the location information report takesplace. Or, the timestamp can indicate a time corresponding to a locationof the VAL UE indicated by the location information report. In anexample, when the location report configuration indicates inclusion ofthe timestamp of the location information report, the timestamp would beincluded in the location information report.

In an example, the location information report from the locationmanagement client (301) to the location management server (302) caninclude all or part of the information shown in Table 1.

TABLE 1 Information element Status Description Set of identities M Setof identities of the reporting VAL users or VAL UEs Triggering event MIdentity of the event that triggered the sending of the report LocationInformation M Location information Timestamp O Timestamp of the locationreportIn Table 1, “M” denotes “mandatory”, and “O” denotes “optional”.

In some embodiments, the timestamp in the location information reportcan take one of several different time formats, such as ISO 8610 (e.g.,yyyy-month-dayTHH:MM:SS), RFC 1123 (e.g., Monday, DD Mon YYYY HH:MM:SSTimeZone), coordinated universal time (UTC: yyyy-mn-ddTHH:MM:SS), andthe like.

In some embodiments, the location information report can include atleast one of several different types of location information, such asE-UTRA cell global identifier (ECGI), multimedia broadcast multicastservices service area identity (MBMS SAI), and geographic coordinates,and other types of location information.

At (S350), upon receiving the location information report, the locationmanagement server (302) can store information included in the locationinformation report in a local memory. For example, the locationmanagement server (302) can update a location of the reporting locationmanagement client (301). If the location management server (302) doesnot have location information of the reporting location managementclient (301) before, then the location management server (302) can juststore the reported location information for that location managementclient (301).

2.2 On-Demand Location Reporting Process

FIG. 4 shows an on-demand location reporting process (400) according tosome embodiments of the disclosure. The process (400) can be performedby a location management server (401) and a location management client(402). During the process (400), in some embodiments, the locationmanagement server (401) can request UE location information at any timeby sending a location information request to the location managementclient (402), which may trigger the location management client (403) toimmediately send a location report.

At (S410), based on configurations such as a periodic locationinformation report timer, or a location information request from otherentities (e.g., another location management client or VAL server), thelocation management server (401) can determine to immediately initiate alocation information request.

At (S420), the location management server (401) sends the locationinformation request to the location management client (402). Forexample, the location information request may include an identity of aVAL user or a VAL UE and specify what type of location information isrequested for the VAL user or the VAL UE.

At (S430), optionally, at the location management client (402), the VALuser or VAL UE can be notified and asked about permission to share itslocation. The VAL user can accept or deny the request. In someembodiments, the location can be shared automatically without furtheruser input.

At (S440), the location management client (402) responds to the locationmanagement server (401) with a location information report containinglocation information identified by the location management server (401)and available to the location management client (402). In someembodiments, the location information report of (S440) can be similar tothe location information report of (S340). For example, the locationinformation report of (S440) can include location information of thelocation management client (402) and a timestamp associated with alocation indicated by the location information. The location informationreport of (S440) may or may not indicate a trigger event for thelocation information report.

At (S450), upon receiving the location information report, the locationmanagement server (401) can update the location of the reportinglocation management client (402). In an example, if the locationmanagement server (401) does not have location information of thereporting location management client (402) before, the locationmanagement server (401) can just store the reporting locationinformation of the location management client (402).

2.3 Client-Triggered or VAL Server-Triggered Location Reporting Process

FIG. 5 shows a client-triggered or VAL server-triggered locationreporting process (500) according to some embodiments of the disclosure.The process (500) can be performed by a first location management client(501A) or a VAL server (501B), a location management server (502), and asecond location management client (503). During the process (500), insome embodiments, the first location management client (501A) or the VALserver (501B) can initiate a request for location information of a VALuser or VAL UE corresponding to the second location management client(503). In response, the location management server (502) can obtain therequested location information and report to the first locationmanagement client (501A) or the VAL server (501B).

At (S510), the first location management client (501A) (e.g.,corresponding to an authorized VAL user or VAL UE) or the VAL server(501B) sends a location reporting trigger to the location managementserver (502) to activate a location reporting procedure for obtainingthe location information of the second location management client (503).

At (S520), the location management server (502) can check whether thefirst location management client (501A) or the VAL server (501B) isauthorized to send a location reporting trigger. Subsequently, dependingon the information specified by the location reporting trigger, thelocation management server (502) can initiate an on-demand locationreporting procedure or an event-triggered location reporting procedurefor requesting location information of the second location managementclient (503).

At (S530), once the location information of the second locationmanagement client (503) is available at the location management server(502), a location information report can be sent to the first locationmanagement client (501A) or the VAL server (502). In some embodiments,the location information report of (S530) can be similar to the locationinformation report of (S340). For example, the location informationreport of (S530) can include location information of the locationmanagement client (503) and a timestamp associated with a locationindicated by the location information. The location information reportof (S530) may or may not indicate a trigger event for the locationinformation report.

In an embodiment, before the first location management client (501A) canrequest location information from the location management server (502),the first location management client (501A) can perform a registrationprocess to register with the location management server (502). Forexample, the first location management client (501A) can send atimestamp request to the location management server (502) to request atimestamp be added to location information reports from the locationmanagement server (502). After that, the location information responsemessages from the location management server (502) will each include atimestamp in response to a respective location query from the firstlocation management client (501A).

In an embodiment, for a location information query of the VAL server(501B) to the location management server (502), there is no registrationprocess between the VAL server (501B) and the location management server(502). The location management server (502) can optionally send aresponse with a timestamp to the VAL sever (501B).

2.4 Location Information Subscription and Notification Process

FIG. 6 shows a location information subscription and notificationprocess (600) according to some embodiments of the disclosure. Theprocess (600) can be performed by a VAL server (601), a locationmanagement server (602), a location management client (603), and a 3GPPcore network (604). During the process (600), the VAL server (601) cansubscribe to location information of a VAL user or VAL UE correspondingto the location management client (603) to the location managementserver (602). The location management server (602) can provide alocation information notification to the VAL server (601) based on asubscription configuration. The process (600) can be employed fortracking a UE, for example. In place of the VAL server (601), otherentities, such as a location management client, can use the process(600) to subscribe for the location information corresponding to thelocation management client (603) and receive location informationnotifications accordingly from the location management server (602).

At (S610), the VAL server (601) can transmit a location informationsubscription request to the location management server (602) tosubscribe to location information of one or more VAL users or VAL UEs.Each VAL user or VAL UE may correspond to a location management client.In the steps below, subscription and reporting of the locationinformation of the VAL user or VAL UE corresponding to the locationmanagement client (603) are used as an example. The location informationsubscription request may indicate what type of location information isneeded, a set of events for triggering a location report from thelocation management client (603), an interval for periodically providinga location information notification, and/or the like. The locationinformation subscription request may indicate that location informationfrom the 3GPP core network (604) (referred to as supplementary locationinformation) is needed.

At (S620), the location management server (602) receives the latestlocation information of the VAL UE corresponding to the locationmanagement client (603) as per a location report procedure. For example,the location report procedure can be an event-triggered locationreporting process (e.g., the process (300)) or an on-demand locationreporting process (e.g., the process (400) triggered by a periodicallocation report timer configured based on the location informationsubscription request at S610). Before receiving the latest locationinformation of the VAL UE, the location management server (602) maycommunicate with the location management client (603) to configure thelocation reporting. For example, as performed in the process (300), someevents may be configured in the location management client (603) fortriggering the location reporting.

At (S630), the location management server (602) may optionally receivethe location information of the VAL UE from 3GPP core network (604). Forexample, if the indication for supplementary location information isincluded in the subscription request of S610, the UE locationinformation can be obtained from the 3GPP core network (604).

At (S640), based on a location information subscription configurationprovided by the location information subscription request at (S610)(e.g., a periodical location information report timer), the locationmanagement server (602) can determine to report the latest user locationinformation of the location management client (603) to the VAL server(601). For example, the location management server (602) can determinethe location information of the VAL UE as received in steps (S620)and/or (S630), including the supplementary location information (ifindicated by the location information subscription request).

At (S650), the location management server (602) transmits a locationinformation notification including the latest location information ofone or more VAL users or VAL UEs to the VAL server (601) (or to thelocation management client that has previously performed a subscriptionto the location management server (602)).

In some embodiments, the location information notification can includeone or more of the following information elements: (1) A list of the VALusers or VAL UEs, of which the location information is notified. (2) Anidentity of a VAL user or VAL UE that subscribes to the locationcorresponding to the location management client (603). (3) An identityof an event that triggered the transmission of the location informationnotification, or an identity of an event that triggered the locationmanagement client (603) to transmit the location information report at(S620). (4) Location information of the VAL users or VAL UEs, of whichthe location information is notified, that, for example, include thelatest location information corresponding to the location managementclient (603). (5) A timestamp of the location report. In an example, atimestamp corresponding to a latest location indicated by the locationinformation corresponding to the location management client (603) isincluded. In an example, a timestamp corresponds to a latest location ofeach of the VAL users or VAL UEs, of which the location information isnotified, is included. In an example, a timestamp corresponding to thetiming when the location information notification is generated isincluded.

In some embodiments, the location information notification from thelocation management server (602) to the VAL server (601) can include allor part of the information flow shown in Table 2.

TABLE 2 Information element Status Description Identities list M List ofthe VAL users or VAL UEs of which location information needs to benotified Identity M Identity of the VAL user or VAL UE subscribed tolocation of another VAL user or VAL UE (NOTE) Triggering event MIdentity of the event that triggered the sending of the notificationLocation Information M Location information Timestamp O Timestamp of thelocation report NOTE: This is used for location management server sendslocation information notification to the VAL user or VAL UE that hassubscribed the location.

In some embodiments, the VAL server (601) may further share the locationinformation in the location information notification to a group of or toanother VAL user or VAL UE.

III. Exemplary Location Reporting Processes

FIG. 7 shows a location reporting process (700) according to anembodiment of the disclosure. The process (700) can be performed by alocation management client of a SEAL. The process (700) can start from(S701) and proceed to (S710).

At (S710), a location reporting configuration can be received at a UEfrom a location management server of the SEAL. The location reportingconfiguration can indicate at least one location reporting event fortriggering a location information report from the location managementclient at the UE to the location management server.

At (S720), the location information report can be transmitted to thelocation management server from the location management client at the UEin response to the at least one location reporting event occurring. Inan example, the location information report can include an identity ofthe UE, an identity of the at least one location reporting event thattriggers the location information report, location information of theUE, and a timestamp corresponding to the location information of the UE.In an example, a type of the location information is identified in thelocation reporting configuration.

In an example, a format of the timestamp corresponding to the locationinformation of the UE is in accordance with one of ISO 8610, RFC 1123,and coordinated universal time (UTC). In an example, a type of thelocation information is one of an E-UTRA cell global identifier (ECGI),a multimedia broadcast multicast services service area identity (MBMSSAI), and geographic coordinates. The process (700) can proceed to(S799) and terminate at (S799).

FIG. 8 shows a location reporting process (800) according to anembodiment of the disclosure. The process (800) can be performed by alocation management server of a SEAL. The process (800) can start from(S801) and proceed to (S810).

At (S810), a location reporting configuration can be transmitted to alocation management client of the SEAL at a UE. The location reportingconfiguration can indicate at least one location reporting event fortriggering a location information report from the location managementclient of the SEAL at the UE to the location management server.

At (S820), the first location information report can be received fromthe location management client of the SEAL at the UE. The first locationinformation report can include an identity of the UE, an identity of theat least one location reporting event that triggers the locationinformation report, location information of the UE, and a timestampcorresponding to the location information of the UE. In an example, atype of the location information is identified in the location reportingconfiguration.

In an example, a format of the timestamp corresponding to the locationinformation of the UE is in accordance with one of ISO 8610, RFC 1123,and coordinated universal time (UTC). In an example, a type of thelocation information is one of an E-UTRA cell global identifier (ECGI),a multimedia broadcast multicast services service area identity (MBMSSAI), and geographic coordinates.

At (S830), the location information of the UE can be stored in a memoryat the location management server. The process (800) can proceed to(S899) and terminate at (S899).

IV. Computer System

The techniques described above can be implemented as computer softwareusing computer-readable instructions and physically stored in one ormore computer-readable media. The computer software can be coded usingany suitable machine code or computer language that may be subject toassembly, compilation, linking, or like mechanisms to create codecomprising instructions that can be executed directly, or throughinterpretation, micro-code execution, and the like, by one or morecomputer central processing units (CPUs), Graphics Processing Units(GPUs), and the like.

The instructions can be executed on various types of computers orcomponents thereof, including, for example, personal computers, tabletcomputers, servers, smartphones, gaming devices, internet of thingsdevices, and the like.

FIG. 9 shows a computer system (900) suitable for implementing certainembodiments of the disclosed subject matter. The components shown inFIG. 9 for the computer system (900) are exemplary in nature and are notintended to suggest any limitation as to the scope of use orfunctionality of the computer software implementing embodiments of thepresent disclosure. Neither should the configuration of components beinterpreted as having any dependency or requirement relating to any oneor combination of components illustrated in the exemplary embodiment ofa computer system (900).

Computer system (900) may include certain human interface input devices.Such a human interface input device may be responsive to input by one ormore human users through, for example, tactile input (such as:keystrokes, swipes, data glove movements), audio input (such as: voice,clapping), visual input (such as: gestures), olfactory input (notdepicted). The human interface devices can also be used to capturecertain media not necessarily directly related to conscious input by ahuman, such as audio (such as: speech, music, ambient sound), images(such as: scanned images, photographic images obtain from a still imagecamera), video (such as two-dimensional video, three-dimensional videoincluding stereoscopic video).

Input human interface devices may include one or more of (only one ofeach depicted): keyboard (901), mouse (902), trackpad (903), touchscreen (910), data-glove (not shown), joystick (905), microphone (906),scanner (907), camera (908).

Computer system (900) may also include certain human interface outputdevices. Such human interface output devices may be stimulating thesenses of one or more human users through, for example, tactile output,sound, light, and smell/taste. Such human interface output devices mayinclude tactile output devices (for example, tactile feedback by thetouch-screen (910), data-glove (not shown), or joystick (905), but therecan also be tactile feedback devices that do not serve as inputdevices), audio output devices (such as: speakers (909), headphones (notdepicted)), visual output devices (such as screens (910) to include CRTscreens, LCD screens, plasma screens, OLED screens, each with or withouttouch-screen input capability, each with or without tactile feedbackcapability—some of which may be capable to output two dimensional visualoutput or more than three dimensional output through means such asstereographic output; virtual-reality glasses (not depicted),holographic displays and smoke tanks (not depicted)), and printers (notdepicted).

Computer system (900) can also include human accessible storage devicesand their associated media such as optical media including CD/DVD ROM/RW(920) with CD/DVD or the like media (921), thumb-drive (922), removablehard drive or solid-state drive (923), legacy magnetic media such astape and floppy disc (not depicted), specialized ROM/ASIC/PLD baseddevices such as security dongles (not depicted), and the like.

Those skilled in the art should also understand that term“computer-readable media” as used in connection with the presentlydisclosed subject matter does not encompass transmission media, carrierwaves, or other transitory signals.

Computer system (900) can also include an interface (954) to one or morecommunication networks (955). Networks can for example be wireless,wireline, optical. Networks can further be local, wide-area,metropolitan, vehicular and industrial, real-time, delay-tolerant, andso on. Examples of networks include local area networks such asEthernet, wireless LANs, cellular networks to include GSM, 3G, 4G, 5G,LTE and the like, TV wireline or wireless wide area digital networks toinclude cable TV, satellite TV, and terrestrial broadcast TV, vehicularand industrial to include CANBus, and so forth. Certain networkscommonly require external network interface adapters that attached tocertain general purpose data ports or peripheral buses (949) (such as,for example, USB ports of the computer system (900)); others arecommonly integrated into the core of the computer system (900) byattachment to a system bus as described below (for example Ethernetinterface into a PC computer system or cellular network interface into asmartphone computer system). Using any of these networks, computersystem (900) can communicate with other entities. Such communication canbe uni-directional, receive only (for example, broadcast TV),uni-directional send-only (for example CANbus to certain CANbusdevices), or bi-directional, for example to other computer systems usinglocal or wide area digital networks. Certain protocols and protocolstacks can be used on each of those networks and network interfaces asdescribed above.

The aforementioned human interface devices, human-accessible storagedevices, and network interfaces can be attached to a core (940) of thecomputer system (900).

The core (940) can include one or more Central Processing Units (CPU)(941), Graphics Processing Units (GPU) (942), specialized programmableprocessing units in the form of Field Programmable Gate Areas (FPGA)(943), hardware accelerators for certain tasks (944), graphics adapters(˜˜50), and so forth. These devices, along with Read-only memory (ROM)(945), Random-access memory (946), internal mass storage such asinternal non-user accessible hard drives, SSDs, and the like (947), maybe connected through a system bus (948). In some computer systems, thesystem bus (948) can be accessible in the form of one or more physicalplugs to enable extensions by additional CPUs, GPU, and the like. Theperipheral devices can be attached either directly to the core's systembus (948), or through a peripheral bus (949). In an example, the screen(910) can be connected to the graphics adapter (950). Architectures fora peripheral bus include PCI, USB, and the like.

CPUs (941), GPUs (942), FPGAs (943), and accelerators (944) can executecertain instructions that, in combination, can make up theaforementioned computer code. That computer code can be stored in ROM(945) or RAM (946). Transitional data can be also be stored in RAM(946), whereas permanent data can be stored for example, in the internalmass storage (947). Fast storage and retrieval to any of the memorydevices can be enabled through the use of cache memory, that can beclosely associated with one or more CPU (941), GPU (942), mass storage(947), ROM (945), RAM (946), and the like.

The computer-readable media can have computer code thereon forperforming various computer-implemented operations. The media andcomputer code can be those specially designed and constructed for thepurposes of the present disclosure, or they can be of the kind wellknown and available to those having skill in the computer software arts.

As an example and not by way of limitation, the computer system havingarchitecture (900), and specifically the core (940) can providefunctionality as a result of processor(s) (including CPUs, GPUs, FPGA,accelerators, and the like) executing software embodied in one or moretangible, computer-readable media. Such computer-readable media can bemedia associated with user-accessible mass storage as introduced above,as well as certain storage of the core (940) that are of non-transitorynature, such as core-internal mass storage (947) or ROM (945). Thesoftware implementing various embodiments of the present disclosure canbe stored in such devices and executed by core (940). Acomputer-readable medium can include one or more memory devices orchips, according to particular needs. The software can cause the core(940) and specifically the processors therein (including CPU, GPU, FPGA,and the like) to execute particular processes or particular parts ofparticular processes described herein, including defining datastructures stored in RAM (946) and modifying such data structuresaccording to the processes defined by the software. In addition or as analternative, the computer system can provide functionality as a resultof logic hardwired or otherwise embodied in a circuit (for example:accelerator (944)), which can operate in place of or together withsoftware to execute particular processes or particular parts ofparticular processes described herein. Reference to software canencompass logic, and vice versa, where appropriate. Reference to acomputer-readable media can encompass a circuit (such as an integratedcircuit (IC)) storing software for execution, a circuit embodying logicfor execution, or both, where appropriate. The present disclosureencompasses any suitable combination of hardware and software.

While this disclosure has described several exemplary embodiments, thereare alterations, permutations, and various substitute equivalents, whichfall within the scope of the disclosure. It will thus be appreciatedthat those skilled in the art will be able to devise numerous systemsand methods which, although not explicitly shown or described herein,embody the principles of the disclosure and are thus within the spiritand scope thereof.

What is claimed is:
 1. A method of a service enabler architecture layer(SEAL), comprising: receiving a location reporting configuration at afirst user equipment (UE) from a location management server of the SEAL,the location reporting configuration indicating at least one locationreporting event for triggering a first location information report froma first location management client at the first UE to the locationmanagement server; and transmitting the first location informationreport to the location management server from the first locationmanagement client at the first UE in response to the at least onelocation reporting event occurring, the first location informationreport including: an identity of the first UE, an identity of the atleast one location reporting event that triggers the first locationinformation report, first location information of the first UE, and afirst timestamp corresponding to the first location information of thefirst UE.
 2. The method of claim 1, wherein a format of the firsttimestamp corresponding to the first location information of the firstUE is one of: yyyy-month-dayTHH:MM:SS, Monday, DD Mon YYYY HH:MM:SSTimeZone, and yyyy-mn-ddTHH:MM:SS.
 3. The method of claim 1, furthercomprising: receiving a location information request from the locationmanagement server of the SEAL; and in response to the received locationinformation request, transmitting a second location information reportto the location management server, the second location informationreport including second location information of the first UE and asecond timestamp corresponding to the second location information of thefirst UE.
 4. The method of claim 1, further comprising: transmitting alocation reporting trigger to the location management server to activatea location reporting process for obtaining third location information ofa second location management client of the SEAL at a second UE; andreceiving a third location information report from the locationmanagement server, the third location information report including thethird location information of the second UE and a third timestampcorresponding to the third location information of the second UE.
 5. Themethod of claim 1, wherein a type of the first location informationidentified in the location reporting configuration is one of: an E-UTRAcell global identifier (ECGI), a multimedia broadcast multicast servicesservice area identity (MBMS SAI), and geographic coordinates.
 6. Themethod of claim 1, further comprising: transmitting a locationinformation subscription request including a location informationsubscription configuration to the location management server; andreceiving a location information notification from the locationmanagement server, the location information notification including: anidentity of a third UE, an identity of the first UE, an identity of anevent that triggered the location information notification, latestlocation information of the third UE, and a fourth timestamp associatedwith the latest location information of the third UE.
 7. A method of aservice enabler architecture layer (SEAL), comprising: transmitting froma location management server a location reporting configuration to afirst location management client of the SEAL at a first user equipment(UE), the location reporting configuration indicating at least onelocation reporting event for triggering a first location informationreport from the first location management client of the SEAL at thefirst UE to the location management server; receiving the first locationinformation report from the first location management client of the SEALat the first UE, the first location information report including: anidentity of the first UE, an identity of the at least one locationreporting event that triggers the first location information report,first location information of the first UE, and a first timestampcorresponding to the first location information of the first UE; andstoring the first location information of the first UE in a memory. 8.The method of claim 7, wherein a format of the first timestampcorresponding to the first location information of the first UE is oneof: yyyy-month-dayTHH:MM:SS, Monday, DD Mon YYYY HH:MM:SS TimeZone, andyyyy-mn-ddTHH:MM:SS.
 9. The method of claim 7, further comprising:transmitting a location information request to the first locationmanagement client of the SEAL at the first UE; receiving a secondlocation information report from the first location management client ofthe SEAL at the first UE, the second location information reportincluding second location information of the first UE and a secondtimestamp corresponding to the second location information of the firstUE; and storing the second location information of the first UE at thememory.
 10. The method of claim 7, further comprising: receiving alocation reporting trigger from a first vertical application layer (VAL)server or a second location management client of the SEAL at a secondUE; initiating a location reporting process to obtain third locationinformation of the first UE in response to the location reportingtrigger being received; and transmitting a third location informationreport to the first VAL server or the second location management clientof the SEAL at the second UE, the third location information reportincluding the third location information of the first UE and a thirdtimestamp corresponding to the third location information of the firstUE.
 11. The method of claim 10, wherein the location reporting processis an on-demand location reporting process or an event-triggeredlocation reporting process between the location management server andthe first location management client of the SEAL at the first UE,depending on information of the location reporting trigger.
 12. Themethod of claim 7, further comprising: receiving a location informationsubscription request including a location information subscriptionconfiguration from one of a second VAL server and a third locationmanagement client of the SEAL at a third UE; in response to a locationinformation notification being triggered according to the locationinformation subscription configuration, determining latest locationinformation of one or more UEs including the first UE; and transmittingthe location information notification to the one of the second VALserver and the third location management client of the SEAL at the thirdUE, the location information notification including: an identity of thefirst UE, an identity of the third UE when the location informationsubscription request is received from the third UE, an identity of anevent that triggered the location information notification, the latestlocation information of the first UE, and a fourth timestamp associatedwith the latest location information of the first UE.
 13. The method ofclaim 12, wherein the latest location information of the first UE isdetermined based on location information received from the firstlocation management client of a respective one of the one or more UEs orfrom a core network of a wireless communication network.
 14. The methodof claim 7, wherein a type of the first location information identifiedin the location reporting configuration is one of: an E-UTRA cell globalidentifier (ECGI), a multimedia broadcast multicast services servicearea identity (MBMS SAI), and geographic coordinates.
 15. Anon-transitory computer-readable medium storing instructions that, whenexecuted by a processor, cause the processor to perform a method of aservice enabler architecture layer (SEAL), the method comprises:receiving a location reporting configuration at a first user equipment(UE) from a location management server of the SEAL, the locationreporting configuration indicating at least one location reporting eventfor triggering a first location information report from a first locationmanagement client at the first UE to the location management server; andtransmitting the first location information report to the locationmanagement server from the first location management client at the firstUE in response to the at least one location reporting event occurring,the first location information report including: an identity of thefirst UE, an identity of the at least one location reporting event thattriggers the first location information report, first locationinformation of the first UE, and a first timestamp corresponding to thefirst location information of the first UE.
 16. The non-transitorycomputer-readable medium of claim 15, wherein a format of the firsttimestamp corresponding to the first location information of the firstUE is one of: yyyy-month-dayTHH:MM:SS, Monday, DD Mon YYYY HH:MM:SSTimeZone, and yyyy-mn-ddTHH:MM:SS.
 17. The non-transitorycomputer-readable medium of claim 15, wherein the method furthercomprises: receiving a location information request from the locationmanagement server of the SEAL; and in response to the received locationinformation request, transmitting a second location information reportto the location management server, the second location informationreport including second location information of the first UE and asecond timestamp corresponding to the second location information of thefirst UE.
 18. The non-transitory computer-readable medium of claim 15,wherein the method further comprises: transmitting a location reportingtrigger to the location management server to activate a locationreporting process for obtaining third location information of a secondlocation management client of the SEAL at a second UE; and receiving athird location information report from the location management server,the third location information report including the third locationinformation of the second UE and a third timestamp corresponding to thethird location information of the second UE.
 19. The non-transitorycomputer-readable medium of claim 15, wherein a type of the firstlocation information identified in the location reporting configurationis one of: an E-UTRA cell global identifier (ECGI), a multimediabroadcast multicast services service area identity (MBMS SAI), andgeographic coordinates.
 20. The non-transitory computer-readable mediumof claim 15, wherein the method further comprises: transmitting alocation information subscription request including a locationinformation subscription configuration to the location managementserver; and receiving a location information notification from thelocation management server, the location information notificationincluding: an identity of a third UE, an identity of the first UE, anidentity of an event that triggered the location informationnotification, latest location information of the third UE, and a fourthtimestamp associated with the latest location information of the thirdUE.